Conversation
🧪 Test Suite AvailableThis PR can be tested by a repository admin. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (28)
📝 WalkthroughSummary by CodeRabbit
WalkthroughRelease bump across core, framework, transports, and multiple plugins; added changelog entries and updated Anthropic beta header docs for Azure/Bedrock/Vertex. Migration test seed now includes Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
|
383051c to
90ccf11
Compare
Confidence Score: 4/5Safe to merge after fixing the boolean literal type mismatch in the migration test script. One P1 defect: the new
Important Files Changed
Reviews (1): Last reviewed commit: "v1.4.19 cut" | Re-trigger Greptile |
| ('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, 0), | ||
| ('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, 1) |
There was a problem hiding this comment.
Integer literals
0/1 incompatible with PostgreSQL BOOLEAN column
The calendar_aligned column is defined in Go as bool with gorm:"default:false", which GORM maps to a native BOOLEAN type in PostgreSQL. PostgreSQL does not accept bare integer literals (0, 1) for BOOLEAN columns and will throw ERROR: column "calendar_aligned" is of type boolean but expression is of type integer, causing the PostgreSQL migration test to fail.
Every other boolean column in this same script uses false/true (e.g. send_back_raw_request/send_back_raw_response in the config_providers insert, and enabled in config_log_store), both of which are valid boolean literals accepted by PostgreSQL and modern SQLite (≥ 3.23.0) alike.
| ('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, 0), | |
| ('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, 1) | |
| ('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, false), | |
| ('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, true) |

Summary
This release includes several bug fixes and new features, primarily focusing on Anthropic beta headers support, provider reliability improvements, and enhanced model metadata capabilities.
Changes
anthropic-betaheaders for Azure, Bedrock, and Vertex AI providers with configurable overrides/api/models/detailsendpoint providing model capability metadataType of change
Affected areas
How to test
Validate the changes with the following steps:
The beta headers feature can be configured via the Beta Headers tab in provider configuration or through
beta_header_overridesin provider settings.Screenshots/Recordings
Added documentation screenshots showing the Beta Headers configuration interface for:
Breaking changes
Related issues
This release addresses provider reliability and adds support for Anthropic's beta feature ecosystem across cloud providers.
Security considerations
Checklist
docs/contributing/README.mdand followed the guidelines